Customer administered autoload

ABSTRACT

A system and method for automatically loading a pre-selected value onto a fare card allows a patron to enter or leave a transit system gate without having to add a fare value at a vending machine. The automatic loading provides added convenience and security for the patron. The vehicle for the automatically-loaded value is either a credit card that is pre-authorized for use by the patron, or the patron&#39;s available benefits. The automatic loading process may be utilized to autoload values of benefits only, or to load values from a combination of benefits and credit card transactions. The pre-selected autoload value is loaded onto the fare card at the gate before confirmation that the credit card transaction is authorized. The gate sends a message to a transit central computer that an autoload has occurred. The central computer determines whether benefits are available to fill the request, and forwards a request for the difference to a credit processing company.

RELATED APPLICATIONS

[0001] This application is a continuation in part of U.S. patentapplication Ser. No. 10/104,635 filed Mar. 21, 2002, which claimspriority under 35 U.S.C. 119(e) to provisional U.S. Patent ApplicationNo. 60/277,816 filed Mar. 21, 2001.

FIELD OF THE INVENTION

[0002] This invention relates generally to fare card use in transitsystems, and more specifically to a system for allowing patrons to havevalues automatically loaded onto their fare cards.

BACKGROUND OF THE INVENTION

[0003] The use of fare cards in mass transit systems has reached recordlevels with the introduction of free transfers, unlimited passes, andfare pricing systems based on distance traveled, time of day, and usercategorization including age and frequent user. Automatic farecollection (AFC) presents several advantages over person-to-person cashexchanges including reduced operating costs based upon a decrease inrequired personnel, automation of system accounting, and improvedconvenience and safety for commuters by the elimination of ticket windowlines and ticket purchases for each transit system ride.

[0004] Fare cards are available in various formats including magneticstripe cards, contact smart cards and contactless smart cards. The farecards may be purchased at automatic vending machines utilizingbills/coins, credit, and/or debit cards. The value of the card may belimited to the value of a single transit fare, or may exceed the valueof a single transit fare so that the card may be used for multiplefares. A fare card having a value exceeding one transit fare offers anadvantage of a single financial transaction for multiple rides. Inaddition, since the fare collection systems deduct value automaticallyfor time and/or distance based fares, the rider does not need to computeexact fare amount as long as the amount on the card equals or exceedsthe required fare, and thus, the time the rider spends at a fare carddispensing machine is shortened. Any monetary value remaining on thecard is usable for a subsequent fare. Fare cards also offer theadvantage of being reusable. The transit rider inserts a used card intoan automatic fare vending machines along with a payment means includingbills/coins, or credit/debit cards, and a corresponding added value isstored on the fare card.

[0005] Current automatic vending machines offer the above statedadvantages of reuse of a fare card and quick transaction times. However,due to frequent use of the fare card, a transit patron is unlikely toknow the exact amount on his or her card at any given time. In order todetermine the value before attempting to pass through a transit gate,the patron must have access to a vending machine or another card reader.If the patron attempts to enter the gate without sufficient value on thefare card, he or she will be denied access to the transit system untilvalue is added to the fare card. Thus, the patron will have to seek outa vending machine to add value to the fare card. During peak commuterhours, commuters are often faced with lines at the automatic farevending machines.

[0006] The procedure of loading monetary value onto a fare card requiresthe patron to insert or wave the fare card past the vending machine toread the current value of the card. The patron then selects an actionprompted by the vending machine to add monetary value to the card byeither inserting cash into the vending machine conducting thetransaction utilizing a credit card. The credit card transactionrequires that the patron's credit card be inserted into the vendingmachine. The vending machine then initiates a check through the creditcard company to obtain approval to charge the requested amount. Once amonetary value is deposited into the vending machine or approved viacredit, the patron must re-insert or wave the fare card by a target tohave the requested value added to the fare card. The patron is thenready to utilize the fare card to gain access to the transit system. Theextra time required to add value to the fare card, as well as the needto have cash or a credit card on hand at all time, is inconvenient forthe patron and may cause undue delays for the patron in arriving at hisor her destination.

[0007] Fare cards may also be utilized to support employee benefitsprograms that supply a set monetary value to be used by the employeeeach month for payment of transit fare. To receive the benefit, a patronmust have the monetary value loaded onto the card at a transit vendingmachine. Thus, there is a potential for long patron queues waiting attransit vending machines at the beginning of each month. As the benefitsprogram expands, and is made available to an increasing number ofpatrons, the vendor queues will become frustratingly longer.

[0008] Due their increasing popularity, reusable cards are also utilizedoutside of the transit system environment, also referred to herein as an“out-of-system” environments. An example of an out-of-system environmentis use of a magnetic stripe card or smart card to purchase groceriesand/or other consumer goods. For example, a magnetic stripe or smartcard may be used at grocery stores by a person who is entitled towelfare food benefits awarded by a government agency. Since the benefitis recurring, the card value must be replenished at the issuing agencyor at a designated terminal. Similar to transit system environments,out-of-system environments have the potential of presentinginconveniences to the card users who wish to replenish the card value.

[0009] Therefore, a need remains in mass transit systems to provide forautomatic loading of a monetary value onto fare cards at the railtransit gates and/or bus fare boxes. A further need remains to provideout-of-system environments that automatically load values onto magneticstripe or smart cards.

SUMMARY OF THE INVENTION

[0010] It is an advantage of the present invention to provide a systemfor automatically loading a monetary value onto a fare card, and whichallows patrons to set up their fare cards for an autoload status so thatthey may use their fare cards without periodic reloads at vendingdevices.

[0011] Another advantage of the present invention is to provide a systemthat is “Self Service” oriented for reloading monetary values on farecards at transit gates, bus fare boxes, and other similar transitauthority equipment, in order to reduce program administrative costs,including the costs associated with transit authority personnel andequipment.

[0012] Yet another advantage is to provide convenient payment vehicles,including credit cards and already-established employee benefitsprograms, at initial introduction of the automatic reload system.

[0013] A further advantage is to provide a system that improves thetransit patron's security by eliminating the need for monetarytransactions at a vending machine.

[0014] Another advantage is to provide an automatic reload system thatmay be extended to uses in out-of-system environments.

[0015] In the exemplary embodiment of the present invention, a transitsystem allows patrons to set-up their fare cards for an autoloadfunction, also referred to herein as a “customer administered autoload”system. The system for autoloading a fare card may be used to supportall transit systems including rail systems and bus systems. The autoloadfeature of a transit system allows the transit patron to quickly refreshthe value of his or her fare card by automatically billing the patron'scredit card account, or by automatically applying the patron's employeebenefits. Automatic loading of the monetary value may be exercisedmanually by the patron at a vendor, or automatically at gates or fareboxes which are set up to accept fare card transactions. As disclosedherein, gates are access control devices used in the rail system andfare boxes are access control devices used on buses. Automatic reloadingat the gates or fare boxes allows transit patrons to use fare cardswithout having to periodically reload values onto their fare cards atthe transit vending machines.

[0016] In the exemplary embodiment, the patron utilizes a vendingmachine or another transit facility for setting up the automatic load,i.e. “autoload” feature. During the set-up process, the patron suppliescredit card or other debit-type card information and a pre-approvedmonetary refresh value. The credit card information is then stored onthe patron's fare card. If a monetary value on the fare card does notcover a required fare, transit gates autoload the pre-approved monetaryvalue to the fare card utilizing the credit/debit card information. Inthe exemplary embodiment, the patron may utilize more than one credit ordebit vehicle. For example, if a patron is supplied with transit fareallowances through his or her employer, the patron may have a benefit ofa line of credit for a set time period. The customer administeredautoload system may be set-up to exhaust the benefit line of creditbefore utilizing the patron's credit card information to initiate an addvalue procedure.

[0017] Implementation Approach. In an exemplary embodiment of thepresent invention, the initial implementation of the customeradministered autoload system provides transit patrons with instructionson how to setup the customer administered autoload at a transit vendingmachine. The customer administered autoload program of the exemplaryembodiment is separate from other transit system programs because itrequires a specific fare card technology. Thus, the patron must besupplied with an autoload-capable fare card which has a valid serialnumber that is recognized by the customer administered autoload system,only. In other embodiments, the customer administered autoload programis utilized by patrons that participate in other transit benefitsprograms, such that the autoload feature will only use the credit cardas the payment vehicle when the benefits program allotment has beenexhausted.

[0018] Set Up. In the exemplary embodiment of the present invention,setup for participation in customer administered autoload is offered toany patron at a transit vending machine. When used in out-of-systemenvironments, the customer administered autoload is offered to patronsat specified out-of-system terminals. Conditions for participation inthe autoload program may be required. For example, the fare card and/orpatron must be registered with the transit authority, the fare card hasbeen used in a credit transaction that has been approved, the currenttransaction meets a minimal price for either the product or valueloaded, and/or the card expiration date is at least six months out.Certain conditions may prohibit the patron from either setting up theautoload function on his or her fare card or completing an autoloadtransaction. For example, the autoload fare card is either not set upfor autoload, the credit card used in the current transaction is not thesame one used to initially setup autoload, e.g., the primary accountnumber, and expiration date, and/or the card is setup for autoload for aspecific value or product, and the customer has asked for a differentvalue or product.

[0019] In an exemplary method for setting up autoload on a fare card, atransit vending machine appends the registered fare card number to acredit card authorization request message (EUC6). The central computersends a reply message (EUC2) to verify that the fare card is registeredand has address data specified. The vendor applies the above criteria,and offers autoload to the patron as an option if the criterion is met.If the patron accepts the autoload option, one or two explanatory panelsof data are presented on the vendor display explaining autoload andreferencing the patron educational material. If the patron then verifiesand accepts the option of autoload, the card is initialized forautoload.

[0020] The vendor initializes the fare card for autoload by setting anautoload bit on the fare card to “on”. In addition, the credit cardPrimary Account Number (PAN) and expiration date is recorded on the farecard as well as a specified product or value. The vendor sends a specialfare card detail transaction data message (EU65) to the central computerwhich then documents the autoload setup. Since the patron is offeredsetup on the various conditions as discussed above, e.g., the creditcard used in the current transaction is not the same one used toinitially setup autoload, the process of changing to a different creditcard is supported via the setup processing.

[0021] In the exemplary embodiment of the present invention, the farecard also may be initialized for autoload at a Point of Issue (POI)device in the transit system and/or in an out-of-system environment.This allows the customer service of the issuing authority to issue afare card to the patron that is setup for autoload. This is of primaryimportance to, for example, bus only riders that may not have access tovending machines. A credit card autoload may also be accomplished at atransit vending machine. The autoload at a vending machine provides aquick transaction since the credit card is not required, and the overalltime to complete the transaction is reduced.

[0022] Withdrawal from the Program. There are several options forwithdrawal from the autoload program. A first option is for the patronto discontinue use of the fare card such that no further autoloads willbe performed. The customer may also visit a transit authority vendorwhere he or she may request withdrawal from the autoload program. Ifwithdrawal is requested, the vendor sets the autoload bit to “off” via amenu specification. The withdrawal request then is reported via an EUxxmessage element type (MET) to the central computer. The customer mayalso return the fare card to the transit authority or the issuingauthority where it can be reinitialized.

[0023] The Autoload Process. Once a fare card is initialized forautoload, the patron may use the autoload card as a “normal” fare card.When the autoload-initialized fare card is presented at a gate or farebox, the patron-selected value or product will automatically be added tothe card, providing the fare card meets the autoload criteria. The loadwill be documented as an autoload MET in an EU65 and maintained as partof the fare card transaction history. In the exemplary embodiment of theinventive method, the criteria for autoloading includes verifying thatthe autoload bit is set to “on”, verifying that the value of avalue-based card has dropped below a specified level, and/or verifyingthat the expiration of a pass is within a set number of days or-rides.In the exemplary embodiment, the autoload criteria is downloaded to thegates and fare boxes. Alternatively, the values used in the abovecriteria may be hardcoded at the processing device, i.e., the gates andbus fare boxes.

[0024] The above described automatic loading is a “card-based” autoload.That is, presentation of the fare card initiates the automatic loadingof values or benefits. A “directed” autoload of a smart card isinitiated by, for example, the central computer, wherein the centralcomputer is continuously looking for a fare card which is scheduled foran autoload. Typically, benefits become available on specific days, suchas the first of the month. A directed autoload system requiresconsiderable central computer resources to keep track of the status ofthe potential thousands of cards which must be loaded with the benefitsvalues. In contrast, the central computer of a card-based autoload doesnot have to monitor card use. Rather, the presentation of a card at avending machine or a gate initiates the autoload process. A transitsystem of the exemplary embodiment has the capability for providing boththe card-based autoload as well as the directed autoload.

[0025] Continuing with the autoload process example, in addition to thenormal EU65 transaction, the gate/bus fare box sends a force postmessage (EUC4) to the central computer to indicate that an autoloadtransaction occurred. The central computer recognizes the force postmessage (EUC4) as an autoload transaction and performs specialprocessing. First, the central computer verifies whether the card holderparticipates in a benefits program. If the benefits program qualifiesfor the requested transaction, the value of the benefits program isutilized to satisfy part or all of the requested transaction. If thevalue of the benefits program is sufficient to satisfy all of therequest, no further action is taken. Otherwise, the central computertransforms the force post into a credit authorization request. Anapproved credit authorization request prompts the central computer tocreate a confirmation entry in an autoload or a credit transactiondatabase. A declined credit authorization request prompts the centralcomputer to add the fare card number to a negative list.

[0026] Negative list. The negative list is utilized in a negative listprocess to initiate a “last load recall” rather than rejecting the card.This feature provides a less harsh response to an expired/bad creditcard that is specified as the autoload vehicle. The negative listprocess includes setting the autoload enable bit to “off” and recallingthe last product or value load performed.

[0027] Messages. The transit gate or fare box of the exemplaryembodiment displays a variety of messages to the patron. For example, ifa payment vehicle, e.g., the credit card, is within forty-five (45) daysof expiration, each use of the autoload-initiated card will cause awarning message to be displayed to the patron at the transit gate orfare box. If the payment vehicle has expired, autoload will not beperformed, and the patron will be refused entry when the value, thenumber of rides or the time for the pass is exhausted. If an autoloadtransaction is processed, the gate or fare box flashes a messageindicating that the fare card has been autoloaded with a specifiedamount.

Acronyms Utilized in the Description

[0028] The following detailed description utilizes a number of acronyms.While definitions are typically provided with the first instance of eachacronym, for convenience, a list of the acronyms and abbreviations usedherein along with their respective definitions are shown below. ACRONYMDEFINITION ACI ACI Worldwide, Inc. AFC Automatic Fare Collection(system) EUB5 A Benefits Claim Request EUC4 Debit/Credit FinancialTransaction Advice Message (Force Post) EUBX Message set for Benefitsrequests. EUCx Message set for Debit/Credit processing. EUxx Unsolicitedaudit data (produced on schedule) message. These types of messages areevent driven. The sender expects only an acknowledgment. EU65 FarecardDetail Transaction Data Message ISO International Standards OrganizationMessage Any data sequence initiated by the CC or SMADS, commencing withthe sequence ECxx, EIxx, ERxx, ETxx, or EUxx, as defined in thisdocument. MET Message Element Type PAN Primary Account Number(Credit/Debit card number) PIN Personal Identification Number POI PointOf Issue equipment. A PC-based system that initializes and changes dataon a fare card. Fare card A microprocessor-based transceiver that cancommunicate with a host computer. Used for a proximity electronic farecollection system for rapid transit or toll road applications. SMADSStation Monitor And Display System. This is a PC-based system that isphysically in the system mezzanines and acts as the collection point forall device transactions (e.g., gates, vendors, PLE, and exit fare) tothe CC.

BRIEF DESCRIPTION OF THE DRAWINGS

[0029] The present invention will be better understood from thefollowing detailed description of a preferred embodiment of theinvention, taken in conjunction with the accompanying drawings in whichlike reference numerals refer to like parts and in which:

[0030]FIG. 1 is an illustration of a system for implementing CustomerAdministered Autoload;

[0031]FIG. 2 is an illustration of the benefits autoload process;

[0032]FIG. 3 is an illustration of the credit card autoload process;

[0033]FIG. 4 illustrates the autoload table and list generation; and

[0034]FIG. 5 illustrates the credit card autoload initializationprocess.

DESCRIPTION OF A PREFERRED EMBODIMENT

[0035]FIG. 1 illustrates the customer administered autoload system 10 ofa preferred embodiment of the present invention. The customeradministered autoload system 10 allows a transit patron to quicklyrefresh a value on a transit fare card 34, e.g., a fare card utilizedfor a proximity electronic fare collection system for rapid transit ortoll road applications, by automatically billing the patron's creditcard account, or by automatically applying benefits provided to thepatron by a third party, e.g., an employer, “Fare cards” used in thisdescription includes contact smart cards, contactless smart cards and/ormagnetic stripe cards. Also, although the following descriptionemphasizes a transit system use of autoload, it should be appreciatedthat the autoload process also may be utilized in out-of-systemenvironments, for example, retail stores. The autoload feature is anoption that can be exercised manually by the patron at a transit vendingmachine 30 (vendor) or automatically at gates 28 or bus fare boxes 26. Atransit vending machine 30 is a device operated by patrons thatdispenses—fare media in exchange for value, e.g., cash, fare cardtrade-in, benefits, debit card, or credit card. In a preferredembodiment of the present invention, the autoload processes, as shown inFIGS. 2 through 5, are implemented with minimum administrative supportby the transit authority staff. The customer administered autoload isconvenient for a transit patron to use and allows the transit patron tochange the payment method, or vehicle, at his or her convenience.

[0036] Continuing with FIG. 1, values autoloaded onto the fare cards 34may be obtained by means of a benefits autoload process or a credit cardautoload process. The benefits autoload process is a pre-paid process asany available benefits are stored in a patron benefits data base 14 inthe transit central computer 12. The credit card autoload process is apost-pay process which occurs through a debit/credit transaction 20.

[0037] Patron Benefits Autoload. The benefits autoload feature chargesall fare card value adds to the patron's benefits account 14 stored inthe transit authority central computer 12. The setup for the benefitsautoload is fully automatic. The patron only has to register with hisemployer or other benefits provider, and his associated data is loadedin the Patron Benefits table 14 through the transit authority or otherauthorized personnel. In a preferred embodiment of the invention, apatron may request the benefit provider to initiate an autoload at railgates 28 and/or bus fare boxes 26. A patron who requests the busautoload option automatically receives the benefits at the transitdevices 28, 26 or at a transit vending machine 30.

[0038] Benefits available to a patron are stored in the central computer12 in a benefits data base 14 which associates a patron to a specificfare card serial number. The fare card automatically receives thebenefit value when the benefit becomes available and the card ispresented at a rail gate 28 or a bus fare box 26. A Benefits Applicationexecuted by the processor 18 of the central computer 12 prepares a tableof the available benefits for benefits autoload processing. The autoloadtable includes the serial numbers of eligible fare cards 34, the sumtotal of the available benefits for each eligible fare card, and anassigned control number to identify the benefit. The autoload table ofthe eligible fare card 34 is sent to the rail gates 28 over a transitsystem communication network 36. At least a portion of the autoloadtable 40 is downloaded 38 via, e.g., a portable device or bus depotcomputer (not shown), to each bus fare box 26.

[0039]FIG. 4 illustrates the central computer autoload processes 100 forcreating an autoload list 102, which is performed at the transitauthority central computer 12. The benefits autoload table 40 is createdat regular intervals, for example, each day at 1:00 am, in order toupdate patrons access to available benefits. In a first step 104, theprocessor 18 of the central computer 12 loads benefits from the patronbenefits database 14 which associates eligible fare cards with aparticular benefit value. A current autoload (AL) table is generated andstored 106 in the autoload table data base 40. The table may includesseveral columns, as shown in Table 1, associated with each fare card.Autoload tables of other embodiments may contain any combination ofpatron information data. TABLE 1 Auto Load Columns fare card controlbenefit purse status status create Effective Last AL serial numberamount code Greenwich GMT GMT list load number Mean Time GMT (GMT)

[0040] The fare card serial number is pre-registered for a specificpatron. A control number assigned to each benefit resides on theautoload table 40 and is also recorded in the patron benefits data base14. The control number is one byte (0 to 255) that recycles. For apatron that has only monthly benefits with one purse, the control numberwill recycle approximately every twenty-one (21) years withoutduplication. The control number eliminates the possible problem of apatron “double dipping” into available benefits as further explainedbelow. The purse code identifies a specific use for the purse as thecard may have multiple purses, e.g., parking only, bus only. The pursecode offers flexibility for purse values on the fare card 34. The statusidentifies the current status for the fare card 34, e.g., whether thecard is pending, delivered, etc. The Greenwich Mean Time (GMT) is theactual time of creation of the status, the table, and the most recentautoload list download. The effective date indicates when a benefit isavailable for situations in which, for example, benefits arepre-authorized and downloaded ahead of time. The effective date preventsthe benefit from delivery before that date.

[0041] In step 108, an autoload list, which is a subset of the autoloadtable, is downloaded to the gates and fare boxes 26, 28. An “AS OF DATE”is set as a unique identifier for the autoload list. Each autoload listentry requires ten (10) bytes, and contains the following data fields:Data Field Bytes Serial number 6 Amount 2 Control number 1 Purse code 1

[0042] Thus, one megabyte of memory is required at each device for each100,000 entries on the autoload list. In the preferred embodiment of theinvention, patrons may have multiple autoload entries if they areeligible for more than one benefit.

[0043] The control number is a one (1) byte binary field with a numericrange of 0 thru 255. The autoload process of the preferred embodimentdoes not use zero (0) for a range of 1 thru 255. A control number isassigned to a benefit when it is loaded into the benefits table 14. Thecentral computer 12 assigns the next control number in sequential order.The assigning of numbers is cyclic, i.e., the next number after 255is 1. When multiple benefits are created for a patron, a single uniquecontrol number is assigned to each benefit created. A single autoloadtable entry is created for that single control number. The value oramount related to the control number is the total amount of the benefitscontaining that control number. Only active benefits are used to createentries on the autoload table.

[0044] The expiration dates of the benefits determine the order in whichthey are used to satisfy requests for benefits. For example, a benefitwhose expiration date is Mar. 21, 2002 will be used before a benefitwith an expiration date of Mar. 30, 2002. In the preferred embodiment,the number of entries in the autoload table may be limited dependingupon what is available on a fare card. For example, a patron may belimited to access to only four benefits at one time. When there are morethan four control numbers, the four control numbers that have theearliest expiration dates are loaded on the autoload table. Expiredbenefits are replaced on the autoload table with newer benefits. TABLE 2Control Number Examples Ctl # Benefit Expiration Priority 201 A  6 Jan 1B 10 Jan 3 C 11 Jan 4 202 A  8 Jan 2 203 A 30 Jan 9 204 A 15 Jan 6 B 17Jan 7 C 29 Jan 8 205 A 12 Jan 5

[0045] Table 2 illustrates a patron's available benefits. Controlnumbers 201 and 204 have three benefits each and control numbers 202,203, and 205 have one benefit each. Only the four control numbers withthe earliest expiration dates are selected for the autoload listdownloaded to the gates 28 and fare boxes 26. Thus, benefits 203A, 201A,201B, and 202A are selected for the autoload list. If benefit 202A isclaimed totally in an autoload transaction, then it is not a candidatefor the next created autoload table. A subsequent autoload list willcontain control numbers 201, 203, 204, and 205.

[0046] The Benefits Autoload Process. The benefits autoload process 110is illustrated in FIG. 2. When a patron uses his or her fare card at agate or fare box 26, 28, a control number and amount is read from thefare card 34, step 112. The control number and amount read from the farecard 34 is compared to the control number and amount from the autoloadlist downloaded from the central computer, step 114. If the controlnumber and amounts on the card match those in the autoload list in thedevice 26, 28, then the card is not eligible for an autoload, step 116.If the control number and amount do not match, then the device adds theautoload list amounts to the value remaining, i.e., the general purse,on the fare card, and updates the control number and amount on the farecard 118. The amounts loaded and their control numbers are sent to thecentral computer via an EUB5 message which requests a claim for theamount loaded. The device 26, 28 then performs its normal fare deduction120 on the fare card, and sends an EU65 message to the central computerdescribing both the autoload and the value deducted from the card. Thecentral computer 12 determines whether adjustments are required 122,adjusts the debit if necessary 124, and updates the patron benefits database 14, step 126. The transactions and messages from the bus fare box26 are stored in the fare box 26 and uploaded to the central computer 12by means of a depot computer.

[0047] If a patron is eligible for multiple benefits, then the autoloadlist stored in the gates and fare boxes 28, 26 will include the controlnumbers and amounts for each benefit. The maximum number of controlnumbers allowed for each fare card is dependent upon the memoryavailable on the fare card 34, and the available memory at the transitdevices 28, 26. Each control number requires one (1) byte, and eachamount requires two (2) bytes. Thus, if the patron is eligible for fourbenefits, twelve (12) bytes will be required to store the information onthe fare card 34.

[0048] In a preferred embodiment of the invention, a patron's availablebenefits are automatically loaded onto his or her fare card according toa set of autoload rules that are downloaded to the gates 28 and fareboxes 26. For example, the autoload process is initiated when the valueremaining on the fare card drops below a threshold amount, or on aspecific calender date. More than one rule may be applied. The rules areestablished by transit authority operators, and may be based uponenrollment agreements between the customer i.e., the patron's employer,and the transit authority. If a patron wishes to add value to his or herfare card, transit vending machines, which directly communicate with thecentral computer in real time, allow the patron a variety of options foradding value to the fare card. In the preferred embodiment, the farecard applies a ceiling as to the value that is on the card. For example,the value remaining on the card will not exceed $200. The ceiling may beestablished for all fare cards, or according to the autoload rules.Technology limitations and/or security measures may also dictate themaximum value supported on a fare card. The autoload process of thepreferred embodiment is a card-based autoload, that is, the autoload isinitiated by presentation of the card at a terminal as opposed to beingdirected by the central computer to reload specific cards. Thisdistinction is of importance particularly when multitudes of patronsparticipate in the autoload program. Specifically, card-based autoloadfrees the central computer from tracking card status each time newbenefits are available to participating patrons.

[0049] Withdrawal from the Benefits Autoload Program. The customer,e.g., the employer that authorizes the patron benefits, may remove thepatron from receiving benefits. In a preferred embodiment, the customermay request the transit authority to remove the patron using, e.g., apoint of issue device 42, as shown in FIG. 1. The customer may also haveauthorized access to request a withdrawal utilizing, e.g., a personalcomputer 44 through an Internet link 46 to the transit authority centralcomputer 12. A patron may discontinue use of the fare card, and nofurther autoloads will be performed. Discontinued use may be voluntary,or involuntary in a situation such as termination of employment whereinthe patron turns in the fare card to his or her employer. The transitauthority may also withdraw a patron from the benefits autoload program.For example, a lost fare card may be hot-listed by means of a NegativeList screen which denies a patron any or limited cash-only use of thefare card.

[0050] Benefits Last Load Recall Process. Situations may occur that apatron receives a benefit that is not available. For example, a benefitmay be withdrawn for use after it has already been received by thepatron by means of a benefit autoload or a request at a vending machine.A last load recall process presents various means by which an amount maybe recalled. In one embodiment, the last load recall is a manual processin which the transit authority adjusts the patron's smart benefitsaccount if the recall value is available in the account. In anotherembodiment, the patron's account status indicates a debit amount whichis resolved once a new benefit is added to the patron's account.

[0051] Credit Card Autoload Initialization. The credit card autoloadprocess charges all cash values added to a fare card to the patron'scredit card. To participate in the credit card autoload process, apatron must first register his intent to use his credit card as theautoload source or vehicle. Referring to FIG. 1, the fare card 34 may beregistered for credit card autoload at a transit vending machine 30, apoint of issue device 42, or personal computer 44 through a transitauthority Internet web site 46 as long as these devices have capabilityfor credit/debit processing. In addition, if the Internet web site 46option is used to initialize credit card autoload, the fare card mustalready have been issued to the patron at a point of issue device 42.

[0052] Referring to FIG. 1 and FIG. 5, when a patron presents his or herfare card 34 to the reader/writer 32 of, e.g., a transit vending machine30, the vending machine 30 reads the fare card 160 and offers a varietyof payment options to the patron. If the patron opts to load a valueonto the fare card using a credit card, he or she must present a creditcard for approval by a credit card processing center 22. To accomplishthis, the transit vending machine 30 appends the fare card serial numberto a credit card authorization request (EUC6) sent to the centralcomputer 12. The central computer 12 verifies the fare card 152,including determining whether the fare card is registered in the farecard data base 48. The central computer 12 then requests credit cardauthorization 154 through a debit/credit process 16 in order toestablish communication 20 with a credit card processing center 22. Uponvalidation of the debit/credit process 16, the central computer sends aresponse message (EUC2) to the vending machine 30.

[0053] Upon receipt of the response message (EUC2) 162, the vendor 30determines whether the patron is eligible to participate in the creditcard autoload based upon a number of autoload criterion 164. If thepatron is eligible, the autoload option is offered for selection by thepatron. In a preferred embodiment of the invention, the credit cardautoload process is offered to any patron according one or anycombination of the following autoload criterion:

[0054] 1. The fare card 34 is used in a credit request transaction;

[0055] 2. The fare card 34 is registered in the central computer 12 farecard database 48;

[0056] 3. The fare card 34 is not registered for the benefits autoloadfunction;

[0057] 4. The credit card request transaction is approved;

[0058] 5. The fare card 34 is either not set up for autoload or the cardis set up for autoload and the credit card used in the currenttransaction is not the same credit card that was used to initially setupautoload;

[0059] 6. The fare card 34 is setup for autoload, and the patron hasasked for a different credit card as the payment vehicle;

[0060] 7. The transaction meets a minimal price for the value loaded;and

[0061] 8. The credit card expiration date is at least six months out.

[0062] If the patron accepts the credit card autoload offer 166, one ortwo explanatory panels of data are presented at the vending machine 30explaining the autoload process and referencing any available patroneducational material. If the patron opts to proceed with the credit cardautoload process, the patron is prompted to select the value forautoload, e.g. $20 for each autoload transaction. In the preferredembodiment, the patron also may specify the threshold value fortriggering the autoload process, e.g., the fare card has a value lessthan $5, as well as a maximum value limit for the card. Triggeringevents, threshold values, and maximum limits may be pre-determinedaccording to rules established by the transit authority. The credit cardautoload value represents the monetary amount that will automatically beloaded onto a patron's fare card each time he or she presents the farecard to a gate or fare box, and a triggering event is satisfied. Theautoload value will be added to the fare card up to the maximum valuelimit, or ceiling amount, e.g., $200.

[0063] Upon receipt of all patron selections, the vending machine 30sets up the fare card 34 for autoload 168, and the requested value isadded to the fare card. The autoload data includes one (1) bit of anautoload flag bit which is set to “on” for an approved autoload, nine(9) bytes of “Track 2” data which include the primary account number(PAN) and the expiration date of the credit card, one (1) byte for thepurse code, and two (2) bytes for the autoload amount. Theinitialization is completed by the vending machine 30 transmitting adetail transaction data message (EU65) message to the central computer12. Upon receipt of EU65 message, the central computer 12 updates the afare card data base 48 which contains the serial numbers and patroninformation for all registered fare cards, to indicate that the farecard 34 is initialized for credit card autoload, step 156. If the patrondoes not choose the credit card autoload 166 option, then the requestedmonetary value is added to the fare card 170.

[0064] Credit Card Autoload Process. A patron need only present a farecard that is registered for the credit card autoload process to atransit gate 28 or fare box 26 to have a value added to the fare card 34if the value of the fare card falls below a pre-determined minimum.Referring to FIG. 3, the patron presents a fare card to the gate or farebox 28, 26 and the fare is deducted from the fare card 132. If atriggering event is detected 134, then a patron-specified credit cardautoload value is added to the fare card 136 and the patron is allowedentry. The device 28, 30 displays a message indicating that the farecard was autoloaded. In a preferred embodiment of the credit cardautoload process, the criteria for initiating autoload at the gate isthat the autoload bit of the fare card is set to “on”, and the value ona value-based card is below a specified level. If the payment vehiclestored on the fare card 34 is within, e.g., forty-five (45) days ofexpiration, each use of the fare card 34 causes a warning message to bedisplayed to the patron at the gate or fare box 28, 26. If the paymentvehicle has expired, autoload is not performed and the patron is refusedentry when the fare card value, rides or time is exhausted.

[0065] If the criteria is met, the vending machine 30 sends a force postmessage (EUC4) to the central computer 12. In addition, a detailtransaction message (EU65) containing information about the autoload issent to the central computer 12. This information contains the valueadded to the fare card 34. The central computer 12 recognizes the EUC4as a credit card autoload request, and determines whether any benefitsare available to satisfy the request 138. Any available benefits areapplied to the credit request 140, and the credit card request amount isadjusted accordingly 142. If an additional amount is required to satisfythe request, the EUC4 message is sent to the credit card service company144 for processing. The fare card data base 48 is updated to reflect thetransaction, step 146. If the transaction is not authorized, the updateto the database will include a negative list flag as explained below.

[0066] In the preferred embodiment of the credit card autoload process,bonuses are included in either the credit adjustment 142 or in theupdate of the fare card data base 146 according to pre-determined bonusrules. For example, if a patron requests $20 to be added to his or herfare card by a credit transaction, the patron will receive an actualadded value of $22. Fare cards 34 that are initialized for the creditcard autoload process are not included in the benefits autoload listsent to the devices 28, 26. Patron benefits are applied to the fare card34 by the central computer 12 before being sent as a force post in thecredit card processing 16. In this way all available benefits areapplied by the central computer 12 when processing a credit cardautoload request.

[0067] Transit Authority Support. The autoload system of the preferredembodiment may require administrative effort by the transit authority toensure proper decisions are made when processing a rejected autoloadrequest. The rejection processing needs a qualified administrator toanalyze the rejection data and select a proper recovery option. When thepatron's fare card is automatically loaded in a credit card autoload,the gate 28 generates a EUC4 force post/advice transaction message whichis an ISO 8583 transaction implemented for the debit/credit system. Avalue is added to a patron's fare card before credit authorization isrequested from the issuer, and thus, the transaction could be refusedwhen received by the issuer. Any refused transactions are returned tothe transit authority which must research all refused transactions as anormal part of the debit/credit administrative support and determinewhether a card should be withdrawn or added to a negative list asdescribed below. In other embodiments of the invention, the actionstaken upon a refused credit card authorization are processedautomatically by the central computer 12.

[0068] Negative list. In a preferred embodiment of the credit cardautoload process, when it is determined that the credit card transactionwas refused, the serial number of the fare card may be added to anegative list, or alternatively, the fare card data base 48 is updatedto include an appropriate flag or code in the status of the fare card. Aflag or code indicates the actions that should be taken when the patronnext presents the fare card at a transit device. In the preferredembodiment, the credit card autoload bit on the fare card is set to“off” to disallow further credit card autoload. The patron may reset theautoload by visiting a vending machine and re-initializing the creditcard autoload process utilizing, e.g., another valid credit card.Another action that may be taken to reclaim the credit card autoloadvalue is to debit any available patron benefits. If patron benefits arenot available, then the autoload bit on the fare card is set to “off”,and the fare card is debited to remove the value of the last autoloadfrom the card. The debit may result in a negative value on the fare card34. This will result in the patron being refused entry to the gate, atwhich time, he or she must add value to the fare card at a vendingmachine 30.

[0069] Withdrawal from the Credit Card Autoload Process. The patron maydiscontinue use of the fare card and no further automatic value loadswill be performed. The patron may visit a vending machine 30 to removethe setup bit via a menu specification. This action is reported to thecentral computer via an EU65 message element type (MET), and thepatron's fare card status is updated to reflect the change. The transitauthority may also initiate withdrawal by changing the status in thefare card data base 48 and/or adding the card to a negative list.

[0070] Fare card Requirements. A fare card of a preferred embodiment foruse with the benefits autoload processes requires three (3) bytes ofmemory to store the purse amount and the benefit control number.Multiple available benefits will require additional storage. Forexample, four (4) benefit entries may be stored on a card for a total oftwelve (12) bytes. A fare card for use only with the credit cardautoload process requires three (3) bytes of memory to store the purseamount and a control number and one autoload “on” or “off” bit. Thecombination of the two autoload processes requires the sum total ofstorage space needed for the benefit autoload process and the creditcard autoload process. In the preferred embodiment, read/write accesstime is reduced by accessing only the needed data for certain functions.

[0071] Gate Requirements. The benefits autoload process of the preferredembodiment of the present invention requires one megabyte of devicememory per 100,000 autoload entries in an autoload list. The credit cardautoload does not require gate storage. Each gate is loaded with acomplete benefits autoload list at regular intervals. Benefits are notapplied to a fare card while the gate is receiving the autoload table.This download process presents a window at each gate when a patron cannot receive benefits. This effects of this window may be minimized bycreating and downloading the autoload lists early in the transportationday.

[0072] Fare Box Requirements. The autoload list is loaded into the busfare boxes 26 by a bus depot probe. Bus fare boxes 26 typically have amulti-megabyte table storage capacity, and the number of table entriesdoes not impose a resource problem. However, transfer times are longerutilizing a probe in comparison with the downloads to the transit gates28 since the probe devices have a smaller bandwidth. Thus, it isdesirable to reduce the number of table entries that must be transferredto bus fare boxes 26. One method for reducing the autoload list is tocreate a bus-only autoload list. Patrons who are not registered on thislist do not have access to automatic loading of their benefits at thefare box 26, but they do have the option of credit card autoload.

[0073] Sample Autoload Cases. The following cases and accompanyingtables illustrate the benefits autoload process and the credit cardautoload process of a preferred embodiment of the present invention.Case 1 illustrates a single autoload which first occurs at a transitgate, and Case 2 illustrates a single autoload which first occurs at atransit vending machine. Case 3 illustrates multiple autoload amountsusing a gate first, and Case 4 illustrate multiple autoload amountsusing a vending machine first. Case 5 steps through a typical bus-onlyautoload transaction where the fare card value exceeds a maximum limit.Case 6 illustrates a credit card autoload with available benefits thatare less than the autoload amount. Case 7 is a credit card autoloadwherein the available benefits are greater than the autoload amount.

[0074] Case 1: One Autoload Amount Using a Gate First. Table 3illustrates data at start of day on a fare card, in the autoload listdownloaded to the gates and fare boxes 28, 26, and in the benefits table14 of the central computer 12. TABLE 3 Case 1 Initial Values Fare cardGate Fare Box Central Computer Data Autoload List Autoload List BenefitsTable Ctl#: 0 Ctl#: 123 Ctl#: 123 Ctl#: 123 Amt: 0 Amt: $65.00 Amt:$65.00 Amt: $65.00 Ctl#: 0 Amt: 0 Ctl#: 0 Amt: 0 Ctl#: 0 Amt: 0 Amtremaining: $10.00

[0075] In an Action A, the patron passes through a gate 28 with thefollowing resulting actions, as shown in Table 4:

[0076] a. the gate 28 adds the amount from the benefits autoload (AL)table to Amount Remaining field on the fare card 34 (assuming no minimumlevel trigger);

[0077] b. the gate 28 writes the control number and amount to the farecard 34;

[0078] c. the gate 28 sends a claim confirmation message to the centralcomputer 12 which contains the control number (123) and amount claimed($65.00); and

[0079] d. the central computer 12 creates a claim row and applies theclaim request amount against row 1 on the benefits table.

[0080] In an Action B, the patron tries to get $25.00 of benefits fromthe vending machine 30 at the end of her trip. The vending machine 30sends the benefits request to the central computer 12. The data in therequest message includes the control numbers and the amounts containedon the card. The central computer 12 recognizes that there are no morebenefits for this fare card 34 and returns zero for amount authorized inthe return message to the vending machine 30 which displays that nobenefits are available.

[0081] In an Action C, the patron enters the gate 28 on a return trip.The gate 28 compares the fare card's control number with the controlnumbers in the autoload list table. The control numbers match, andautoload processing will not be initiated. In a last Action D, thepatron enters a bus after leaving the rail system. The fare box 26compares the fare card's control number with the control numbers on theautoload list table. The control numbers match, and autoload processingwill not be initiated. TABLE 4 Case 1 Updated Values After Action A Farecard Gate Fare Box Central Computer Data Autoload List Autoload ListBenefits Table Ctl#: 123 Ctl#: 123 Ctl#: 123 Ctl#: 123 Amt: $65.00 Amt:$65.00 Amt: 65.00 Amt: $0 Ctl#: 0 Amt: 0 Ctl#: 0 Amt: 0 Ctl#: 0 Amt: 0Amt remaining: $75.00

[0082] Case 2: One Autoload amount Using a Vendor First. Table 5illustrates data at start of day on a fare card 34. In a first Action A,the patron uses a vending machine 30 to receive $20.00 of benefits, withthe following resulting actions, as shown in Table 6:

[0083] a. the vending machine 30 sends a benefits request to centralcomputer 12 with control numbers and amounts in the message equal tozero;

[0084] b. the central computer 12 returns a message with an authorizedamount of $65.00 for control number 123;

[0085] c. the patron selects $20.00;

[0086] d. the vendor 30 adds $20.00 to the card's Amount Remaining;

[0087] e. the vendor writes the control number and the amount ($20.00)to the card;

[0088] f. the vendor sends a confirmation message containing the controlnumber and the amount ($20.00) to the central computer 12; and

[0089] g. the central computer 12 creates a claim for $20.00 and reducesthe benefit amount remaining by the same amount. TABLE 5 Case 2 InitialValues Fare card Gate Fare Box Central Computer Data Autoload ListAutoload List Benefits Table Ctl#: 0 Ctl#: 123 Ctl#: 123 Ctl#: 123 Amt:0 Amt: $65.00 Amt: $65.00 Amt: $65.00 Ctl#: 0 Amt: 0 Ctl#: 0 Amt: 0Ctl#: 0 Amt: 0 Amt remaining: $10.00

[0090] TABLE 6 Case 2 Updated Values After a Vendor First TransactionFare card Gate Fare Box Central Computer Data Autoload List AutoloadList Benefits Table Ctl#: 123 Ctl#: 123 Ctl#: 123 Ctl#: 123 Amt: $20.00Amt: $65.00 Amt: $65.00 Amt: $45.00 Ctl#: 0 Amt: 0 Ctl#: 0 Amt: 0 Ctl#:0 Amt: 0 Amt remaining: $30.00

[0091] In an Action B, the patron enters a gate 28. The gate 28 comparesthe fare card's control number with the control numbers on the autoloadlist. The control numbers match, and autoload is not initiated. In anAction C, the patron visits a vending machine 30 at the end of her rideto claim an additional $15.00. The fare for the trip ($2.00) wasdeducted from card's Amount Remaining, now $28.00. The vending machine30 sends a request for benefits to the central computer 12. The requestincludes control number 123 and control number amount of $20.00. Thecentral computer 12 returns an authorized amount of $45.00 for ControlNumber 123. The control number and amount are contained in the returnmessage. The vending machine 30 adds $15.00 to the card's AmountRemaining, writes the control number and $15.00 to the control numberamount on the fare card 34. The vending machine 30 sends a confirmationmessage to the central computer 12 which contains the control number andthe amount ($15.00). The central computer 12 creates a claim for $15.00and reduces the benefit amount remaining by the same amount. TABLE 7Case 2 Updated Values After Action C Fare card Gate Fare Box CentralComputer Data Autoload List Autoload List Benefits Table Ctl#: 123 Ctl#:123 Ctl#: 123 Ctl#: 123 Amt $35.00 Amt: $65.00 Amt: $65.00 Amt: $30.00Ctl#: 0 Amt: 0 Ctl#: 0 Amt: 0 Ctl#: 0 Amt: 0 Amt remaining: $43.00

[0092] In an Action D, the patron enters a bus after leaving the railsystem. The fare box 26 compares the fare card's control number with thecontrol numbers on the autoload list. The control numbers match andautoload is not initiated. The bus ride costs $1.00 which is deductedfrom the fare card 34 for an Amount Remaining of $42.00. In an Action E,the patron visits a vendor 30 the next day to claim an additional$65.00, with the following resulting actions, as shown in Table 8:

[0093] a. the vendor 30 sends request for benefits with the controlnumber 123 and a control number amount of $35.00 to the central computer12;

[0094] b. the central computer 12 subtracts the control number amount of$35.00 dollars from the benefits available ($65.00) for a difference of$30.00;

[0095] c. the central computer 12 returns an authorized amount of $30.00for control number 123, and the vendor 30 displays $30.00 as the maximumamount available;

[0096] d. the patron selects $30.00, and the vendor 30 adds $30.00 tothe card's Amount Remaining;

[0097] e. the vendor 30 writes the control number and adds $30.00 to thecontrol number amount on the card.

[0098] f. the vendor 30 sends a confirmation message to the centralcomputer 12 containing the control number and the amount ($30.00); and

[0099] g. the central computer 12 creates a claim for $30.00 and reducesthe benefit amount remaining by the same amount. TABLE 8 Case 2 UpdatedValues After Action E Fare card Gate Fare Box Central Computer DataAutoload List Autoload List Benefits Table Ctl#: 123 Ctl#: 123 Ctl#: 123Ctl#: 123 Amt: $65.00 Amt: $65.00 Amt: $65.00 Amt: $0 Ctl#: 0 Amt: 0Ctl#: 0 Amt: 0 Ctl#: 0 Amt: 0 Amt remaining: $72.00

[0100] Case 3: Multiple Autoload Amounts Using a Gate First. Table 9illustrates a case where three different jobs are run to create theautoload (AL) table. Three different control numbers are created if thepatron has valid benefits created for him on three different days, andthe patron does not use the fare card during this time period. If allfive (5) benefits are available at the same time, only one controlnumber is created. That is, if all five benefits are available at thestart of an autoload table create job, the job creates only one entry inthe autoload table.

[0101] In a first Action A the patron enters through a gate 28, with thefollowing resulting actions, as shown in Table 10:

[0102] a. the gate 28 compares the fare card control numbers againstnumbers on the autoload list with the result that no matches are foundand all amounts in the autoload list are available for loading;

[0103] b. the gate 28 adds the total of the autoload list amounts to thevalue remaining on the card ($54.00);

[0104] c. the gate 28 writes the control numbers and their amounts tothe card;

[0105] d. the gate 28 sends a claim confirmation message to the centralcomputer containing control numbers (081, 082, and 083) and amountsclaimed ($36.00, $5.00, and $13.00); and

[0106] e. the central computer creates five claim rows and applies theclaim request amounts against rows 1 through 5 on the benefits table.TABLE 9 Case 3 Data after Day 3 Auto Load Processing Fare card Gate FareBox Central Computer Data Autoload List Autoload List Benefits TableCtl#: 0 Ctl#: 081 Ctl#: 081 Day 1 benefits Amt: 0 Amt: $36.00 Amt:$36.00 Ctl#: 081 Ctl#: 0 Ctl#: 082 Ctl#: 082 Amt: $25.00 Amt: 0 Amt:$5.00 Amt: $5.00 Ctl#: 081 Ctl#: 0 Ctl#: 083 Ctl#: 083 Amt: $11.00 Amt:0 Amt: $13.00 Amt: $13.00 Day 2 benefits Ctl#: 0 Ctl#: 082 Amt: 0 Amt:$5.00 Amt remaining: Day 3 benefits $10.00 Ctl#: 083 Amt: $3.00 Ctl#:083 Amt: $10.00

[0107] In an Action B, the patron attempts to get $25.00 of benefitsfrom the vendor 30 after the trip. The vendor 30 sends the benefitsrequest to the central computer 12. The data in the request messageincludes the control numbers and the amounts contained on the card 34.The central computer compares the amounts ($36.00, $5.00, and $13.00)already used from control numbers 081, 082, and 083. These amounts aresubtracted from the benefits available on the benefits table. A zero ornegative difference indicates that no benefits are available. If theprevious claim confirmation was not applied to the benefits thesubtraction result is zero. With $0 balances the result is negative. Thecentral computer 12 returns a message that contains zero as the amountauthorized. The vendor 30 informs the patron that no benefits areavailable. TABLE 10 Case 3 Updated Values After a First Transaction Farecard Gate Fare Box Central Computer Data Autoload List Autoload ListBenefits Table Ctl#: 081 Ctl#: 081 Ctl#: 081 Day 1 benefits Amt: $36.00Amt: $36.00 Amt: $36.00 Ctl#: 081 Ctl#: 082 Ctl#: 082 Ctl#: 082 Amt: $0Amt: $5.00 Amt: $5.00 Amt: $5.00 Ctl#: 081 Ctl#: 083 Ctl#: 083 Ctl#: 083Amt: $0 Amt: $13.00 Amt: $13.00 Amt: $13.00 Day 2 benefits Ctl#: 0 Ctl#:082 Amt: 0 Amt: $0 Amt remaining: Day 3 benefits $64.00 Ctl#: 083 Amt:$0 Ctl#: 083 Amt: $0

[0108] In an Action C, the patron enters a gate 28 on a return trip. Thegate 28 compares the fare card's control number with the control numbersin the autoload list. The control numbers match, and autoload is notprocessed. In an Action D, the patron enters a bus after leaving therail system. The bus fare box 26 compares the fare card's control numberwith the control numbers in the autoload list. The control numbersmatch, and autoload is not processed.

[0109] Case 4: Multiple Autoload Amounts Using a Vendor First. Table 11illustrates a case where three different jobs are run to create theautoload (AL) table. In a preferred embodiment, this job runs everymorning. Three different control numbers are created if the patron hasvalid benefits created for him on three different days, and the patrondid not use the fare card during this time period. If all five (5)benefits are available at the same time, only one control number iscreated. This case uses only general purse benefits. TABLE 11 Case 4Data after Day 3 Auto Load Processing Fare card Gate Fare Box CentralComputer Data Autoload List Autoload List Benefits Table Ctl#: 0 Ctl#:081 Ctl#: 081 Day 1 benefits Amt: 0 Amt: $36.00 Amt: $36.00 Ctl#: 081Ctl#: 0 Ctl#: 082 Ctl#: 082 Amt: $25.00 Amt: 0 Amt: $5.00 Amt: $5.00Ctl#: 081 Ctl#: 0 Ctl#: 083 Ctl#: 083 Amt: $11.00 Amt: 0 Amt: $13.00Amt: $13.00 Day 2 benefits Ctl#: 0 Ctl#: 082 Amt: 0 Amt: $5.00 Amtremaining: Day 3 benefits $10.00 Ctl#: 083 Amt: $3.00 Ctl#: 083 Amt:$10.00

[0110] In an Action A, the patron uses a vendor 30 to receive $40.00 ofbenefits, with the following resulting actions, as shown in Table 12:

[0111] a. the vendor 30 sends a benefits request to the central computer12. The control numbers and amounts in the message are all zero;

[0112] b. the central computer 12 gathers the benefits from the rowsavailable on the benefits table using the sequence in which they werecreated (1 thru 5);

[0113] c. the central computer 12 returns a message for a totalauthorized amount of $54.00 with the control numbers contained in thereturn message (Ctl #081, #082, #083; Amounts $36.00, $5.00 $13.00);

[0114] d. the vendor 30 adds $40.00 to the fare card's Amount Remainingusing the oldest control numbers to create this amount;

[0115] e. the vendor 30 writes the control numbers and amounts to thecard (Ctl #081, #082; Amount $36.00, $4.00);

[0116] f. the vendor 30 sends a confirmation message to the centralcomputer 12 containing the control numbers and the amounts listed above;

[0117] g. the central computer 12 creates claims for the benefits used;and

[0118] h. the central computer 12 reduces the amount remaining on thebenefits table. TABLE 12 Case 4 Updated Values After Action A Fare cardGate Fare Box Central Computer Data Autoload List Autoload List BenefitsTable Ctl#: 081 Ctl#: 081 Ctl#: 081 Day 1 benefits Amt: $36.00 Amt:$36.00 Amt: $36.00 Ctl#: 081 Ctl#: 082 Ctl#: 082 Ctl#: 082 Amt: $0 Amt:$4.00 Amt: $5.00 Amt: $5.00 Ctl#: 081 Ctl#: 0 Ctl#: 083 Ctl#: 083 Amt:$0 Amt: 0 Amt: $13.00 Amt: $13.00 Day 2 benefits Ctl#: 0 Ctl#: 082 Amt:0 Amt: $1.00 Amt remaining: Day 3 benefits $50.00 Ctl#: 083 Amt: $3.00Ctl#: 083 Amt: $10.00

[0119] In an Action B, the patron enters a gate 28, with the followingresulting actions, as shown in Table 13:

[0120] a. the gate 28 compares the fare card's control number with thecontrol numbers in the autoload list—two control numbers match (081 and082) and one does not match (083);

[0121] b. the gate 28 adds the amount ($13.00) for control number 083 tothe Amount Remaining on the card;

[0122] c. the gate 28 writes the control number (083) and amount($13.00) to the card;

[0123] d. the gate 28 sends a claim request message to the centralcomputer 12 containing the control number (083) and amount to beclaimed; and

[0124] e. the central computer 12 applies the claim request amountagainst rows 4 and 5 on the benefits table 14.

[0125] The total amount available for autoload was $54.00, and the totalamount claimed is $53.00. Therefore, row 3 on the benefits table has$1.00 of benefits remaining. The patron must go to a vendor 30 toreceive this last amount of $1.00. The control numbers on the fare cardprevent the patron from receiving this last amount with an autoloadprocess. TABLE 13 Case 4 Updated Values After Action B Fare card GateFare Box Central Computer Data Autoload List Autoload List BenefitsTable Ctl#: 081 Ctl#: 081 Ctl#: 081 Day 1 benefits Amt: $36.00 Amt:$36.00 Amt: $36.00 Ctl#: 081 Ctl#: 082 Ctl#: 082 Ctl#: 082 Amt: $0 Amt:$4.00 Amt: $5.00 Amt: $5.00 Ctl#: 081 Ctl#: 083 Ctl#: 083 Ctl#: 083 Amt:$0 Amt: $13.00 Amt: $13.00 Amt: $13.00 Day 2 benefits Ctl#: 0 Ctl#: 082Amt: 0 Amt: $1.00 Amt remaining: Day 3 benefits $63.00 Ctl#: 083 Amt: $0Ctl#: 083 Amt: $0

[0126] Case 5: Bus Only Autoload where Card Remaining Value Exceeds aCard Maximum Limit. FIG. 14 illustrates a Case 5 for a bus-only autoloadwhere the card remaining value is just below a card maximum limit of$200 with no minimum autoload trigger, i.e., autoload occurs until thelimit is reached. TABLE 14 Case 5 Bus Only Autoload with Maximum LimitFare card Gate Fare Box Central Computer Data Autoload List AutoloadList Benefits Table Ctl#: 0 Ctl#: 123 Ctl#: 123 Amt: 0 Amt: $65.00 Amt:$65.00 Ctl#: 0 Amt: 0 Amt remaining: $195.00

[0127] In an Action A, the patron rides the bus. The fare box 26 adds$5.00 to the Amount Remaining field on the patron's fare card 34. Thefare box 26 also writes the Control Number and amount to the card. Thefare box 26 creates a claim confirmation message containing the controlnumber (123) and amount claimed ($5.00). The bus fare box 26 isscheduled to be probed later in the evening. Table 15 shows the resultsof Action A. TABLE 15 Case 5 Updated Values After Action A Fare cardGate Fare Box Central Computer Data Autoload List Autoload List BenefitsTable Ctl#: 123 Ctl#: 123 Ctl#: 123 Amt: $5.00 Amt: $65.00 Amt: $65.00Ctl#: 0 Amt: 0 Amt remaining: $200.00

[0128] In an Action B, the patron is charged $2.50 for a bus ride. Thepatron then uses the rail system to go to work and back to the bus stopfor a total rail cost of $3.75. The amount remaining on patron's cardjust before getting on the bus is $193.75. Since this is a bus-onlyautoload patron, none of the rail transactions add benefits to the card.The patron gets on a bus to go home. The bus fare box 26 autoloads $6.25to the Amount Remaining field on the patron's fare card. The fare box 26adds the amount to the control number amount on the card. The fare box26 creates a claim confirmation message containing the control number(123) and amount claimed ($6.25). Table 16 shows the results of ActionA. TABLE 16 Case 5 Updated Values After Action B Fare card Gate Fare BoxCentral Computer Data Autoload List Autoload List Benefits Table Ctl#:123 Ctl#: 123 Ctl#: 123 Amt: $11.25 Amt: $65.00 Amt: $65.00 Ctl#: 0 Amt:0 Amt remaining: $200.00

[0129] In an Action C the bus fare boxes 26 are probed. The bus depotsends transactions (EUB5 messages) to the central computer 12. The totalof the two claims is $11.25. The central computer 12 creates two claims,one for $5.00 and another for $6.25, and deducts the amount of theseclaims from benefit amount in Row 1 on the benefits table as shown inTable 17. The above actions can repeat until the benefit amount isreduced to zero or the benefit expires. TABLE 17 Case 5 Updated ValuesAfter Action C Fare card Gate Fare Box Central Computer Data AutoloadList Autoload List Benefits Table Ctl#: 123 Ctl#: 123 Ctl#: 123 Amt:$5.00 Amt: $65.00 Amt: $53.75 Ctl#: 0 Amt: 0 Amt remaining: $200.00

[0130] Case 6: Credit Card Autoload with Benefits Less than the AutoloadAmount. In this case the autoload value is $50, and a minimum limit fortriggering autoload is $7.00. Table 18 shows initial values for Case 6.TABLE 18 Case 6 Initial Values Fare card Gate Fare Box Central ComputerData Autoload List Autoload List Benefits Table P/P Code: 128 Amt:$35.00 Amt: 50.00 Amt remaining: $.50

[0131] In an Action A, the patron enters the rail system at a gate 28.The gate 28 adds $50.00 to the Amount Remaining field on the patron'sfare card 34. The gate 28 sends a force post (EUC4) message to thecentral computer for amount of $50.00. The central computer recognizesthe EUC4 as a credit card autoload request and creates a claim for the$35.00 available on the benefits table. The central computer forwards anEUC4 requests to the credit card processing 22 for the difference of$15.00. The central computer creates a confirmation row for $15.00 asshown in Table 19. TABLE 19 Case 6 Updated Values After Action A Farecard Gate Fare Box Central Computer Data Autoload List Autoload ListBenefits Table P/P Code: 128 Amt: $0 Amt: 50.00 Amt remaining: $50.50

[0132] Case 7: Credit Card Autoload with Benefits Greater than theAutoload Amount. In this case the autoload value is $50, and a minimumlimit for triggering autoload is $7.00. Table 20 shows initial valuesfor Case 7. In an Action A, the patron enters a rail system at a gate28. The gate 28 adds $50.00 to the Amount Remaining field on thepatron's fare card, and sends a force post (EUC4) to the centralcomputer for an amount of $50.00. The central computer 12 recognizes theEUC4 as a credit card autoload request, and creates a claim for the$50.00 available on the benefits table. The central computer creates aconfirmation row for $50.00, as shown in Table 21. TABLE 20 Case 7Updated Values After a First Transaction Fare card Gate Fare Box CentralComputer Data Autoload List Autoload List Benefits Table P/P Code: 128Benefit 1 Amt: 50.00 Amt: $65.00 Amt remaining: $3.50

[0133] TABLE 21 Case 7 Updated Values After Action A Fare card Gate FareBox Central Computer Data Autoload List Autoload List Benefits Table P/PCode: 128 Benefit 1 Amt: 50.00 Amt: $15.0 $53.50

[0134] In an Action B several days later, the patron receives anadditional $20 benefit, as shown in Table 22. In an Action C, the patronenters a rail system at a gate 28. The gate 28 adds $50.00 to the AmountRemaining field on the patron's fare card, and sends a force post (EUC4)to the central computer for an amount of $50.00. The central computer 12recognizes the EUC4 as a credit card autoload request, and creates aclaim for the $35.00 available on the benefits table using both Benefits1 and 2. The central computer 12 forwards an EUC4 message for thedifference of $15.00 to the credit card processing 22. The centralcomputer 12 creates a confirmation row for $15.00 as shown in Table 23.TABLE 22 Case 7 Updated Values After Action B Fare card Gate Fare BoxCentral Computer Data Autoload List Autoload List Benefits Table P/PCode: 128 Benefit 1 Amt: 50.00 Amt: $15.00 Amt remaining: Benefit 2$2.50 Amt: $20.00

[0135] TABLE 23 Case 7 Updated Values After Action C Fare card Gate FareBox Central Computer Data Autoload List Autoload List Benefits Table P/PCode: 128 Benefit 1 Amt: 50.00 Amt: $0 Amt remaining: Benefit 2 $52.50Amt: $0

[0136] Although a preferred embodiment of the invention has beendescribed above by way of example only, it will be understood by thoseskilled in the field that modifications may be made to the disclosedembodiment without departing from the scope of the invention, which isdefined by the appended claims.

We claim:
 1. A system for automatically loading a pre-determined valuefrom a selectable source onto a patron's fare card, the systemcomprising: a central computer having a fare card data base for storingfare card data specific to the fare card; a means for initializing anautoload flag to “on” for automatic loading of the pre-determined valueonto the fare card; and a terminal device in communication with thecentral computer for automatically loading the fare card with thepre-determined value.
 2. The system as in claim 1, wherein theselectable source is at least one benefit that is available to thepatron through an issuing authority, and wherein the central computerfurther comprises means for generating an autoload list containing thevalue of the at least one benefit and a control number for the at leastone benefit and downloading the list to the terminal device, theterminal device further comprising means for comparing the controlnumber of the at least one benefit to at least one control number on thefare card and automatically loading the fare card with thepre-determined value if the control number of the autoload list does notmatch the at least one control number on the fare card.
 3. The system asin claim 2, wherein the autoload flag is a benefit autoload flagcontained in the fare card data base, and wherein the means forinitializing the autoload flag to “on” is controlled by one of theissuing authority, the patron, and the customer.
 4. The system as inclaim 2, wherein the at least one benefit is a plurality of benefits,each benefit of the plurality of benefits having an associated controlnumber.
 5. The system as in claim 1, wherein the selectable source is acredit card, and wherein the autoload flag is stored on the fare card,the terminal device for loading the pre-determined value on the farecard if the autoload flag is “on” and for communicating a force postmessage to the central computer after the pre-determined value is loadedonto the fare card, wherein the central computer further comprises meansfor determining whether at least one benefit value is available in thefare card database to offset the pre-determined value and for processinga credit transaction for a difference between the pre-determined valueand the at least one benefit value.
 6. The system as in claim 5, whereinthe central computer further comprises a negative list for listing thefare cards in which the credit transaction is denied, the negative listfor prompting the terminal device to set the autoload flag on the farecard to “off”.
 7. The system as in claim 5, wherein the means forinitializing the fare card for automatic loading of the pre-determinedvalue is a transit vending machine.
 8. The system as in claim 7, whereinthe transit vending machine utilizes at least one criterion to determinewhether the patron is eligible for the automatic loading of thepre-determined value on the fare card.
 9. The system as in claim 1,wherein the terminal device is one of a transit system rail gate and atransit system bus fare box.
 10. The system as in claim 1, wherein thefare card is at least one of a contactless smart card, a contact smartcard, and a magnetic stripe card.
 11. A method for an automaticcard-based loading process for loading a benefits value onto a farecard, the method comprising: generating an autoload list comprising atleast one benefit available, for use with the fare card, a first valuefor the at least one benefit, and a first control number associated withthe each at least one benefit; initializing the fare card with a storagearea for storing an amount remaining, a second value and a secondcontrol number; reading the second value of the at least smart and thesecond control number from the fare card to a transit gate; comparingthe first control number to the second control number; if the firstcontrol number is different than the second control number, adding thefirst value for the at least one benefit to the amount remaining andupdating the amount remaining on the fare card with the result; settingthe second control number equal to the first control number; setting thesecond value equal to the first value; and updating the first value ofthe autoload list to zero if the second value is set equal to the firstvalue; and if the first control number is the same as the second controlnumber, terminating the automatic loading process.
 12. The method ofclaim 11, wherein a central computer generates the autoload list,further comprising the step of downloading the autoload list to thetransit gate.
 13. The method of claim 11, wherein the a partial value ofthe first value is added to the amount remaining, and wherein the firstvalue of the autoload list is updated as the difference between thefirst value and the partial value.
 14. The method of claim 11, furthercomprising the step of reading the amount remaining, and if the amountremaining is above a minimum level, then terminating the automaticloading process.
 15. The method of claim 11, wherein the at least onebenefit is a plurality of benefits having at least one control number,and a plurality of first values associated with the at least one controlnumber, and wherein the step of
 16. A method for an automatic loadingprocess for loading a pre-selected credit card value onto a fare card,the method comprising: initializing the fare card with a storage areafor storing an amount remaining, credit card data, and an autoload flag;and reading the flag value; if the flag value is “on”, adding thepre-selected credit card value to the amount remaining on the fare card;and sending the credit card data and the pre-selected credit card valueto a credit processing means, if the flag value is “off”, terminatingthe automatic loading process.
 17. The method of claim 16, wherein thefare card is at least one of a smart card and a magnetic stripe card.18. The method of claim 16, wherein the credit processing means is acentral computer, further comprising the steps of, determining whetherpatron benefits are available; if the patron benefits are available,subtracting at least a portion of the patron benefits from thepre-selected credit card value; initiating a credit process forrequesting a credit transaction from a credit card processing company.19. The method of claim 18, further comprising the step of receiving oneof an approval or a denial from the credit card processing company; andif a denial is received, adding the fare card to a negative list,wherein the negative list is utilized to set the flag value to “off”.